Repository navigation
Linux build: fixed appimagetool version with retries (fixes the 0.30.0 release) - #85
Merged
Merged
Conversation
…a fallback The 0.30.0 release build failed on Linux only: GitHub answered "504 Gateway Timeout" for appimagetool's "continuous" download (twice, and also for 1.9.1), while 1.9.0 downloads fine. build_linux.sh now gets appimagetool 1.9.0 (APPIMAGETOOL_VERSION to change it), retries a few times, and falls back to the continuous build if that file can't be had. A fixed version also means every build is packed by the same tool. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… between builds GitHub's release downloads answered 504 on and off (also for 1.9.0 on the next try, and also with a cache-busting query), so a few quick retries were not enough. build_linux.sh now tries for up to a few minutes, switching between 1.9.0 and the continuous build, and the CI keeps the tool in GitHub's Actions cache, so later builds don't download it at all. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…appimagetool as fallback With appimagetool downloaded, the next run failed one step later: appimagetool fetches the AppImage runtime from GitHub itself, without retries, and got the same 504. build_linux.sh now fetches the runtime (two rounds) and, if GitHub can't deliver it, uses the runtime at the start of appimagetool (an AppImage itself: the first --appimage-offset bytes), and passes it with --runtime-file. Tested: an AppImage built this way runs and reports its update information. Both files are cached in CI. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The 0.30.0 release build failed on Linux only, in its last step: GitHub's download of appimagetool (the AppImage packing tool) answered 504 Gateway Timeout, on the first run and on the re-run. The app itself built and its tests passed; Windows and both Macs succeeded.
Cause: GitHub fails to deliver appimagetool's
continuousfile (and1.9.1) at the moment, while1.9.0downloads fine.Fix (
build_linux.shonly):APPIMAGETOOL_VERSIONto change it), so every build is packed by the same tool;Merging this runs the build again and publishes 0.30.0 (its tag doesn't exist yet). No version change, no program change.
Generated by Claude Code